Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA00430; Thu, 7 Apr 94 12:10:19 -0600
Received: from wilgate.wiltel.com by alaska.et.byu.edu; Thu, 7 Apr 1994 07:58:29 -0600
Received: from hal01.wiltel.com by wilgate.wiltel.com with SMTP id AA27409
(5.67b/IDA-1.5 for <misckit@alaska.et.byu.edu>); Thu, 7 Apr 1994 09:00:24 -0500
Received: from atg by hal01.wiltel.com (NX5.67d/NX3.0S)
id AA08774; Thu, 7 Apr 94 08:36:35 -0500
Received: from wtg62 by atg.wiltel.com (NX5.67d/NX3.0M)
id AA08645; Thu, 7 Apr 94 08:56:22 -0500
From: Craig Kelley <craig_kelley@wiltel.com>
Message-Id: <9404071356.AA08645@atg.wiltel.com>
Received: by wtg62 (NX5.67d/NX3.0X)
id AA00466; Thu, 7 Apr 94 08:56:20 -0500
Date: Thu, 7 Apr 94 08:56:20 -0500
Received: by NeXT.Mailer (1.100)
Received: by NeXT Mailer (1.100)
To: misckit@alaska.et.byu.edu
Subject: Re: MiscKit.pkg
Another possible reason for splitting things up into separate libraries is for programs that are not dependent on the Appkit. Not all programs on the NeXT are GUI related (oh, blasphemy). There may be classes from the MiscKit that I would like to use but I don't want to have to link in the appkit since I don't use a GUI (servers and such).
---
Craig L. Kelley
WilTel Advanced Technology Group
craig_kelley@wiltel.com
>From: "David Aspinall" <dave@circus.yorku.ca>
>Subject: Re: MiscKit.pkg
>
>My $.02:
>...
>What I would like is to .. maybe .. split the kit up into logical units.
>...
>What I'm thinking of is kinda a hierarchy of dependance. Sort of like
>how you (probably) couldn't use IndexingKit without using the Appkit
>(although I haven't tried this). So we might start with
>
>MiscFoundation
> MiscString and other base level data structures
>
>MiscFind
> Its already a partioned project, why not a separate library.
> Dependant on a compiled MiscFoundation library.
>
>MiscAppkitExtensions
> Views, buttons, sliders, anything that is directly connected to
> the appkit, or maybe MiscInterfaces. I know the palettes are
> already separate libraries, but they could be consolidated.
> Dependant on a compiled MiscFoundation library.
>
>
>Anyway, the only reason I see this as having any merit (as an idea) is to
>collect sections that are not changing as often, and hold them at one